Thanks for PR @harmyderoman. Indeed they are not needed but semantically making example readable that calling those functions causes rest of the logic to stop. Besides navigateTo is likely to return a promise which preserving chain is better than discarding.

@pi0 Every time I tried return navigateTo and got the error Uncaught (in promise) Error: Infinite redirect in navigation guard.
It works fine without return

It shouldn't. I'll investigate.

Would you share a reproduction @harmyderoman? 🙏

Sorry guys, I did that infinity loop by trying to run return navigateTo(to.path). 😄
So stupid mistake.
It's just not so clear from the docs what this function returns and how to use it properly.

No worries @harmyderoman and indeed thanks for sharing the cause. I think we might have improved redirectTo to avoid such loops.

Cool! So I'll close this PR.
Thank you for your great work!

No worries @harmyderoman and indeed thanks for sharing the cause. I think we might have improved redirectTo to avoid such loops.

I also did that infinity loop by trying to run return navigateTo(to.path) .So stupid mistake.

What is the correct writing method？
@pi0 @harmyderoman

@lixiaofa if it's not fixed in new version, try it without return

You should not navigate to the current path as that will perform an extra navigation. Just return:

if (whitelist.includes(to.path)) {
  return
}

You can read more on https://router.vuejs.org/guide/advanced/navigation-guards.html#navigation-guards.

@lixiaofa if it's not fixed in new version, try it without return

All permissions will be separated if they do not return.
Failed to achieve the effect of routing guard.

You should not navigate to the current path as that will perform an extra navigation. Just return:

if (whitelist.includes(to.path)) {
  return
}

You can read more on https://router.vuejs.org/guide/advanced/navigation-guards.html#navigation-guards.

Thank you very much！